System and method for creation of function-based mechatronic objects

ABSTRACT

A system, method, and computer readable medium. A method includes receiving requirements for a mechatronics object and receiving functions for the mechatronics object. The method includes assigning the functions to respective ones of components and operations and linking the requirements to respective ones of the functions. The method includes storing the mechatronics object, including the linked requirements and functions.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application claims the benefit of the filing date of U.S.Provisional Patent Application 61/238,414, filed Aug. 31, 2009, for“System, Method, and Computer Program Product for Functional MechatronicObjects”, which is hereby incorporated by reference.

This application includes some subject matter in common withcommonly-assigned, concurrently-filed U.S. patent application Ser. No.______ for “System and Method for Use of Function-Based MechatronicObjects”, which is hereby incorporated by reference.

TECHNICAL FIELD

The present disclosure is directed, in general, to systems and methodsfor use in computer-aided design, manufacturing, engineering,prototype/test, maintenance, modeling, and visualization (individuallyand collectively, “CAD” and “CAD systems”) and in product lifecyclemanagement (“PLM”) and other systems.

BACKGROUND OF THE DISCLOSURE

Many manufactured products are first designed and modeled in CADsystems, and PLM systems are used by manufacturers, retailers,customers, and other users to manage the design, use, maintenance, anddisposal of various products. Improved systems are desirable.

SUMMARY OF THE DISCLOSURE

Various embodiments include a system, method, and computer readablemedium. A method includes receiving requirements for a mechatronicsobject and receiving functions for the mechatronics object. The methodincludes assigning the functions to respective ones of components andoperations and linking the requirements to respective ones of thefunctions. The method includes storing the mechatronics object,including the linked requirements and functions.

The foregoing has outlined rather broadly the features and technicaladvantages of the present disclosure so that those skilled in the artmay better understand the detailed description that follows. Additionalfeatures and advantages of the disclosure will be described hereinafterthat form the subject of the claims. Those skilled in the art willappreciate that they may readily use the conception and the specificembodiment disclosed as a basis for modifying or designing otherstructures for carrying out the same purposes of the present disclosure.Those skilled in the art will also realize that such equivalentconstructions do not depart from the spirit and scope of the disclosurein its broadest form.

Before undertaking the DETAILED DESCRIPTION below, it may beadvantageous to set forth definitions of certain words or phrases usedthroughout this patent document: the terms “include” and “comprise,” aswell as derivatives thereof, mean inclusion without limitation; the term“or” is inclusive, meaning and/or; the phrases “associated with” and“associated therewith,” as well as derivatives thereof, may mean toinclude, be included within, interconnect with, contain, be containedwithin, connect to or with, couple to or with, be communicable with,cooperate with, interleave, juxtapose, be proximate to, be bound to orwith, have, have a property of, or the like; and the term “controller”means any device, system or part thereof that controls at least oneoperation, whether such a device is implemented in hardware, firmware,software or some combination of at least two of the same. It should benoted that the functionality associated with any particular controllermay be centralized or distributed, whether locally or remotely.Definitions for certain words and phrases are provided throughout thispatent document, and those of ordinary skill in the art will understandthat such definitions apply in many, if not most, instances to prior aswell as future uses of such defined words and phrases. While some termsmay include a wide variety of embodiments, the appended claims mayexpressly limit these terms to specific embodiments.

BRIEF DESCRIPTION OF THE DRAWINGS

For a more complete understanding of the present disclosure, and theadvantages thereof, reference is now made to the following descriptionstaken in conjunction with the accompanying drawings, wherein likenumbers designate like objects, and in which:

FIG. 1 depicts a block diagram of a data processing system in which anembodiment can be implemented in accordance with disclosed embodiments;

FIG. 2 depicts an exemplary user interface of a function navigator thatmay be implemented using a data processing system in support of theprocesses in accordance with disclosed embodiments;

FIG. 3 depicts a block diagram of the different types of data that canbe combined in a functional component of a mechatronics object inaccordance with disclosed embodiments; and

FIG. 4 depicts a flowchart of a process in accordance with disclosedembodiments.

DETAILED DESCRIPTION

FIGS. 1 through 4, discussed below, and the various embodiments used todescribe the principles of the present disclosure in this patentdocument are by way of illustration only and should not be construed inany way to limit the scope of the disclosure. Those skilled in the artwill understand that the principles of the present disclosure may beimplemented in any suitably arranged device. The numerous innovativeteachings of the present application will be described with reference toexemplary non-limiting embodiments.

In general, mechatronics refers the synergistic combination ofmechanical engineering, electrical/electronic engineering, computerengineering, control engineering, systems design engineering, and othertechnical disciplines to create, design and manufacture useful products.The concept phase in the overall design process of a mechatronics systemis the first time where the architect thinks about the physicalimplementation. The architect must ensure that the implementation isconformant with the requirements and has a basic design structure thatenables an efficient detailed design and production.

Today there is no integrated mechanism in place to seamlessly tracerequirements down to the multi-disciplinary design and implementation ofa given product and/or system. The collaboration of multi disciplines isdifficult because there is no joint data structure in place that is akind of interlink between the disciplinary data structures.

Some systems are capable of maintaining requirements, functions anddisciplinary data in a data base. One can match the various datastructures by creating link between items in the data base from a puredata point of view. There is no specific design context forinterdisciplinary concept design in conventional systems.

In conventional systems each item has a specific design context whichmakes the design of multi-disciplinary product designs hard to grasp fordesigners/engineers. Prior systems just look at items as data objectsthat can be managed in a data base. This makes it impossible to supporta creative design process required to produce a mechatronics conceptdesign.

Disclosed embodiments include systems and methods to facilitate thephysical concept design of a product based on a functional designapproach, include a common “linking” structure. A functional model andrelated mechanisms are used to link this model to requirements andenrich this model with interdisciplinary implementation data.

FIG. 1 depicts a block diagram of a data processing system in which anembodiment can be implemented, for example as a CAD or PLM systemconfigured to perform processes as described herein. The data processingsystem depicted includes a processor 102 connected to a level twocache/bridge 104, which is connected in turn to a local system bus 106.Local system bus 106 may be, for example, a peripheral componentinterconnect (PCI) architecture bus. Also connected to local system busin the depicted example are a main memory 108 and a graphics adapter110. The graphics adapter 110 may be connected to display 111.

Other peripherals, such as local area network (LAN)/Wide AreaNetwork/Wireless (e.g. WiFi) adapter 112, may also be connected to localsystem bus 106. Expansion bus interface 114 connects local system bus106 to input/output (110) bus 116. I/O bus 116 is connected tokeyboard/mouse adapter 118, disk controller 120, and 110 adapter 122.Disk controller 120 can be connected to a storage 126, which can be anysuitable machine usable or machine readable storage medium, includingbut not limited to nonvolatile, hard-coded type mediums such as readonly memories (ROMs) or erasable, electrically programmable read onlymemories (EEPROMs), magnetic tape storage, and user-recordable typemediums such as floppy disks, hard disk drives and compact disk readonly memories (CD-ROMs) or digital versatile disks (DVDs), and otherknown optical, electrical, or magnetic storage devices.

Also connected to I/O bus 116 in the example shown is audio adapter 124,to which speakers (not shown) may be connected for playing sounds.Keyboard/mouse adapter 118 provides a connection for a pointing device(not shown), such as a mouse, trackball, trackpointer, etc.

Those of ordinary skill in the art will appreciate that the hardwaredepicted in FIG. 1 may vary for particular implementations. For example,other peripheral devices, such as an optical disk drive and the like,also may be used in addition or in place of the hardware depicted. Thedepicted example is provided for the purpose of explanation only and isnot meant to imply architectural limitations with respect to the presentdisclosure.

A data processing system in accordance with an embodiment of the presentdisclosure includes an operating system employing a graphical userinterface. The operating system permits multiple display windows to bepresented in the graphical user interface simultaneously, with eachdisplay window providing an interface to a different application or to adifferent instance of the same application. A cursor in the graphicaluser interface may be manipulated by a user through the pointing device.The position of the cursor may be changed and/or an event, such asclicking a mouse button, generated to actuate a desired response.

One of various commercial operating systems, such as a version ofMicrosoft Windows™, a product of Microsoft Corporation located inRedmond, Wash. may be employed if suitably modified. The operatingsystem is modified or created in accordance with the present disclosureas described.

LAN/WAN/Wireless adapter 112 can be connected to a network 130 (not apart of data processing system 100), which can be any public or privatedata processing system network or combination of networks, as known tothose of skill in the art, including the Internet. Data processingsystem 100 can communicate over network 130 with server system 140,which is also not part of data processing system 100, but can beimplemented, for example, as a separate data processing system 100.

Disclosed embodiments include new systems engineering processes thatclose the gap between requirements engineering and discipline specificimplementation through the ability to store the functional model whichprovides a discipline-independent definition of a system's functionswhich can be mapped to multiple disciplines for implementation. Theseinclude processes to get to a mechatronics concept design by using asystem such as data processing system 100 for defining and managingrequirements; functional decomposition of the mechatronics system into ahierarchical representation based on function groups, function subgroupsand functional units; linking of requirements and functions; definingthe mechatronics concept of the mechatronics systems containingmechanical design (shape, kinematics and dynamics), electrical design(sensors and actuators), and automation software design (cams, logicbehavior, sequence of operation); and mapping the disciplinary conceptdata to the functional model in one integrated design context.

Various embodiments include user interactions to provide a reusablemechatronics component that can include geometries, kinematics anddynamics for a detailed 3D-design, a sensor-actuator list for anelectrical layout, a behavior description of the machine for theautomation engineering, and simple simulation models for designverification, among other data.

Various embodiments include a design and engineering environment forconcept mechanical, electrical and automation design. Variousembodiments include deliver quick and easy ways to simulate behavior ofmachine and corresponding controllers (PLC or motion).

Various embodiments include gaming-quality physics as an integral partof the design experience. Users will be able to “turn on” their designsand visualize all aspects of physical behavior.

Various embodiments include physics and human behavior into the designprocess to increase behavioral design testing, causing potential designproblems to be found sooner and increasing product quality, and to make3D design engaging and dynamic. Using embodiments disclosed herein, auser has no need to wait until virtual commissioning in order tovisualize the behavior of the mechatronics system.

FIG. 2 depicts an exemplary user interface of a function navigator 200that may be implemented using a data processing system 100 in support ofthe processes described herein. In this figure, the function navigator200 shows a primary function 202 of a mechatronics component, which isfurther divided into main functions 204 and auxiliary functions 206.

Each function node can include a component container 208 and anoperations container 210, and sub-functions 212. Each function can belinked to one or more requirements 214.

Every function node can contain a component container and operationcontainer. The component container is to represent the components whichare used to realize this function. The operation container is torepresent the operations which belong to this function. According tovarious embodiments, all components can be added into componentscontainer node, and one function may have multiple components.

In some embodiments, all the functions with the same type in the samelevel (functions have the same direct parent node) are numbered and haveone number index respectively. According to the creation time order,they are numbered from 1 to N. For example, if one function node C1 has3 children, two A and one B, then the two A will be numbered to A1 andA2 respectively and B will be numbered to B1. If another B is added,then this new comer will be numbered as B2.

The name of function node can be generated by “Function Lettercode”+index+“−”+Name. For instance, if there is one function, and itstype is A, its type index is 2, its name is “motor”, then the functiontree node name will be <A2−“motor”>.

The functional root node can be created and displayed in FunctionNavigator while user creates a new part. The system interacts with theuser to create a Function Node through, for example, a popup menu ofFunction Navigator. A Function Node can represent Function object in theFunction Navigator.

According to disclosed embodiments, a Function object has belowattributes and properties:

-   -   1. Function Type. The type definition complies with IEC        IEC61346-2-2000 standard, known to those of skill in the art.    -   2. Parameter: Defines the parameter name (string) and its value        (string) for the function.    -   3. Requirements: Defines the requirement names (string) and        values (string) associated with function. Note that in a typical        implementation, the requirements are part of their structure and        linked to functions, and the function tree includes a        representation of the actual requirements from the requirements        structure linked to a specific function, and not a property of        the function objects themselves.    -   4. Name (string)

FIG. 3 depicts a block diagram 300 of the different types of data thatcan be combined in a functional component of a mechatronics object asdescribed herein. The functional component 302 can be used to store thediscipline-independent aspects of the system defining what functionsmust be implemented by the different discipline specific models, anddoes not necessarily carry the details of a single specificimplementation of each function.

Functional component 302, shown as part of systems engineering andrequirements engineering (SE & RE) block 304, is linked to requirements306 as described above. Functional component 302 can include MechanicalEngineering assembly data 308, which itself can include CAD data 310 andphysics data 311.

Functional component 302 can also include software programming elementssuch as sequence of operations 312 and CAM data 314, which can becreated using and linked to engineering tools 316. As described above,these elements typically describe or define the functional requirementsfor the element, not a specific implementation. For example, thecomponent can include a specification which defines the sequence ofoperations 312, but may not include the specific sequence of operationsor coding for any specific implementation.

Functional component 302 can also include ECAD and hydraulicsinformation such as sensor/actuator data 318, which can be linked toECAD/Hydraulics data 320. As another example of how the functionalcomponent 302 will typically include specification and definitional dataas opposed to implementation-specific data, for sensors and actuators,the functional component 302 defines what sensing and actuationfunctions are needed, but need not define in detail the sensors andactuators.

Functional component 302 can be stored and used for a detailedsimulation and for virtual commissioning, in one or more specificsimulations 322.

As described above, according to various embodiments, the functionalcomponent 302 is a definition of what the system or product must do inenough detail to allow the different disciplines to work in parallel ondetailed design but without discipline specific design information.

According to various embodiments, the system can store the assignment ofrequirements to functions and from functions to modules and components.The system can store a set of operations defining the functions and cansimulate them to verify their correctness. Various operations are linkedto the functions. The system can therefore generate and store a set ofspecifications for the mechanical/electrical/automation engineers in theform of required movements (including speeds, accelerations, vectors,timing, 3D clearances), any of which can be executed in a simulation.This shortens the product development lifecycle by allowing moreparallel development.

FIG. 4 depicts a flowchart of a process in accordance with disclosedembodiments. Various steps in the process may be performed repeatedly,concurrently, or in a different order.

The system receives requirements for a mechatronic object (step 405). Insome cases, the mechatronic object will correspond to a product. A“product” can be a complete physical product or any other physicalassembly or subassembly unless otherwise indicated. Receiving, as usedherein, can include receiving via an interaction with a user, loadingfrom a storage, receiving from another device or system, for exampleover a network, or otherwise.

The system receives functions (or functional components) for themechatronic object (step 410). Each of the functions of the mechatronicobject can include such functional information as physics definitions,sensor and actuator definitions, function and logic definitions, andother such mechanical, electrical, automation, or other definitions anddata as described herein.

The system assigns the functions of the mechatronic object to respectiveones of components and operations (Step 415). The components andoperations are assigned according to which module or component fulfillsthe various required functions.

The system links each of the requirements to respective ones of thefunctions (step 420). This step can include an interaction with a user,and assures that each requirement is fulfilled by one or more of thedefined functions.

The system stores the mechatronic object, including the linkedrequirements and functions with mechanical/electrical/automationdefinitions (step 425).

The system can simulate the structure and operation of the mechatronicobject (step 430).

The stored mechatronic object can then be used, for example, as areusable product definition in a product lifecycle management or othersystem (step 435).

Those skilled in the art will recognize that, for simplicity andclarity, the full structure and operation of all data processing systemssuitable for use with the present disclosure is not being depicted ordescribed herein. Instead, only so much of a data processing system asis unique to the present disclosure or necessary for an understanding ofthe present disclosure is depicted and described. The remainder of theconstruction and operation of data processing system 100 may conform toany of the various current implementations and practices known in theart.

It is important to note that while the disclosure includes a descriptionin the context of a fully-functional system, those skilled in the artwill appreciate that at least portions of the mechanism of the presentdisclosure are capable of being distributed in the form of ainstructions contained within a machine-usable, computer-usable, orcomputer-readable medium in any of a variety of forms, and that thepresent disclosure applies equally regardless of the particular type ofinstruction or signal bearing medium or storage medium utilized toactually carry out the distribution. Examples of machine usable/readableor computer usable/readable mediums include: nonvolatile, hard-codedtype mediums such as read only memories (ROMs) or erasable, electricallyprogrammable read only memories (EEPROMs), and user-recordable typemediums such as floppy disks, hard disk drives and compact disk readonly memories (CD-ROMs) or digital versatile disks (DVDs).

Although an exemplary embodiment of the present disclosure has beendescribed in detail, those skilled in the art will understand thatvarious changes, substitutions, variations, and improvements disclosedherein may be made without departing from the spirit and scope of thedisclosure in its broadest form.

None of the description in the present application should be read asimplying that any particular element, step, or function is an essentialelement which must be included in the claim scope: the scope of patentedsubject matter is defined only by the allowed claims. Moreover, none ofthese claims are intended to invoke paragraph six of 35 USC §112 unlessthe exact words “means for” are followed by a participle.

1. A method for creation of a mechatronics object, comprising: receivingrequirements for a mechatronics object in a data processing system;receiving functions for the mechatronics object in the data processingsystem; assigning the functions to respective ones of components andoperations by the data processing system; linking the requirements torespective ones of the functions by the data processing system; andstoring the mechatronics object, including the linked requirements andfunctions, in the data processing system.
 2. The method of claim 1,wherein the functions include physics definitions.
 3. The method ofclaim 1, wherein the functions include electrical definitions.
 4. Themethod of claim 1, wherein the functions include automation definitions.5. The method of claim 1, further comprising simulating the structureand operation of the mechatronics object.
 6. The method of claim 1,wherein at least one of receiving requirements and receiving functionsis performed via an interaction with a user.
 7. The method of claim 1,further comprising using the mechatronic object as a reusable productdefinition in a product lifecycle management system.
 8. The method ofclaim 1, further comprising performing a functional decomposition of themechatronics object into a hierarchical representation based on functiongroups, function subgroups and functional units.
 9. A data processingsystem comprising a processor and accessible memory, the data processingsystem particularly configured to perform the steps of: receivingrequirements for a mechatronics object; receiving functions for themechatronics object; assigning the functions to respective ones ofcomponents and operations; linking the requirements to respective onesof the functions; and storing the mechatronics object, including thelinked requirements and functions.
 10. The data processing system ofclaim 9, wherein the functions include physics definitions.
 11. The dataprocessing system of claim 9, wherein the functions include electricaldefinitions.
 12. The data processing system of claim 9, wherein thefunctions include automation definitions.
 13. The data processing systemof claim 9, wherein the data processing system is also configured toperform the step of simulating the structure and operation of themechatronics object.
 14. The data processing system of claim 9, whereinat least one of receiving requirements and receiving functions isperformed via an interaction with a user.
 15. The data processing systemof claim 9, wherein the data processing system is also configured toperform the step of using the mechatronic object as a reusable productdefinition in a product lifecycle management system.
 16. The dataprocessing system of claim 9, wherein the data processing system is alsoconfigured to perform the step of performing a functional decompositionof the mechatronics object into a hierarchical representation based onfunction groups, function subgroups and functional units.
 17. A tangiblecomputer-readable medium encoded with computer-executable instructionsthat, when executed, cause a data processing system to perform the stepsof: receiving requirements for a mechatronics object; receivingfunctions for the mechatronics object; assigning the functions torespective ones of components and operations; linking the requirementsto respective ones of the functions; and storing the mechatronicsobject, including the linked requirements and functions.
 18. Thecomputer-readable medium of claim 17, wherein the functions includephysics definitions.
 19. The computer-readable medium of claim 17,wherein the functions include electrical definitions.
 20. Thecomputer-readable medium of claim 17, wherein the functions includeautomation definitions.
 21. The computer-readable medium of claim 17,further encoded with instructions that, when executed, cause the dataprocessing system to perform the step of simulating the structure andoperation of the mechatronics object.
 22. The computer-readable mediumof claim 17, wherein at least one of receiving requirements andreceiving functions is performed via an interaction with a user.
 23. Thecomputer-readable medium of claim 17, further encoded with instructionsthat, when executed, cause the data processing system to perform thestep of using the mechatronic object as a reusable product definition ina product lifecycle management system.
 24. The computer-readable mediumof claim 17, further encoded with instructions that, when executed,cause the data processing system to perform the step of performing afunctional decomposition of the mechatronics object into a hierarchicalrepresentation based on function groups, function subgroups andfunctional units.